-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a "Write your first test" page to the Get Started section #1777
Conversation
🏓 @heitortsergent I've addressed some of the feedback you offered last time we spoke 🙇🏻 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for the delay @oleiade! I finally got around to reviewing the changes you've made, I left a few comments with some edits, and some style guide changes. Let me know what you think, I think this new guide looks good!
Co-authored-by: Heitor Tashiro Sergent <[email protected]>
Co-authored-by: Heitor Tashiro Sergent <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the changes @oleiade. 🙇
What?
As we agreed during our latest meetup, this PR adds a "Write your first test" page to the Getting Started section.
It aims to cover a gap between installing k6, and "Running k6", as we realised we had not introduced users to scripting in the logical flow yet. This PR aims to bridge that gap, and links to a lot of useful resources users might find useful on their onboarding experience with k6.
@heitortsergent this is really a draft on my side, you should feel free to propose whatever you see fit 👍🏻 Also, I've noticed we have some pages in our documentation which might repeat this information, we might want to also reorganize/regroup it somehow 🙇🏻
Checklist
npm start
command locally and verified that the changes look good.docs/sources/next
folder of the documentation.